Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1608

reference
456-tree-1
name
1608
tree-preservation-order

undefined

456-tpo-1
uprn
address-text
point
POINT (-1.044551 50.883426)
geometry
MULTIPOLYGON (((-1.044367 50.883406,-1.044375 50.883442,-1.044400 50.883475,-1.044441 50.883501,-1.044492 50.883518,-1.044549 50.883525,-1.044606 50.883519,-1.044658 50.883503,-1.044699 50.883478,-1.044726 50.883445,-1.044736 50.883409,-1.044728 50.883373,-1.044702 50.883340,-1.044662 50.883314,-1.044611 50.883297,-1.044554 50.883291,-1.044496 50.883296,-1.044445 50.883312,-1.044403 50.883338,-1.044376 50.883370,-1.044367 50.883406)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL